Generating edit suggestions for transforming digital documents

ABSTRACT

Techniques for generating edit suggestions for transforming digital documents are implemented in a digital medium environment. According to various implementations, a digital document is parsed to extract a digital page, and page elements of the digital page that are editable. A graphical user interface (GUI) is then output that identifies the page elements that are editable. The GUI, for instance, includes a suggestions menu with different edit suggestions that each correlate to different respective page elements. A user may then interact with individual edit suggestions to edit the different page elements, such as by adding, removing, or revising digital content of the page elements. The described techniques, for example, automatically identify editable page elements of a digital page and output edit suggestions for editing the page elements.

BACKGROUND

A variety of different systems are available for creating and publishingdigital documents, including web pages, social media platforms, onlinesales platforms, and so forth. For instance, content creation systemsenable users to generate and arrange digital content such as digitalimages, text, and multimedia to create different digital documents. Thedigital documents can then be published for general online access.

While conventional content creation systems enable a wide variety ofdifferent digital documents to be created and published, they lack theability to provide techniques for generating and editing digital contentthat don't require some form of technical knowledge on the part of auser. For instance, consider a scenario where a user wishes to editvisual aspects of a web page. In a conventional content creation system,the user would typically be required to have technical knowledge ofdifferent element types and how they relate to the structure andappearance of the web page. To edit a Hypertext Markup Language (HTML)document, for example, a user would typically be required to leverage an<img> tag to edit digital images, a <div> tag to manage groups of webpage elements, and so forth. Thus, conventional content creation systemsrequire manual user interaction via complicated content languages andare thus inefficient from both user and system perspectives.

In addition to requiring technical knowledge by a user, conventionalsystems fail to provide guidance regarding how different attributes of adigital document are editable. For instance, consider a web page of anonline sales platform that offers a particular item for sale. The webpage includes a variety of different visual features, such as a banner,a picture of the item for sale, an item description box, an item price,and so forth. Further, the visual features have different visualattributes, such as size, color, and position on the web page. Whileconventional content creation systems enable the different visualfeatures and attributes to be edited, such systems typically do notprovide guidance regarding which of the features are editable, and howediting particular features may affect an overall impression of the webpage.

Thus, conventional content creation systems typically require aconsiderable technical knowledge and time expenditure on a user's partto understand which features of a digital document are editable, and howediting the features may affect the digital document. In addition torequiring considerable human resources, such conventional systemsconsume excessive system resources as well. For instance, processor andmemory resources that would otherwise be available for other computingtasks may be relegated to the repetitive task of responding to userinput while the user is attempting to determine which elements of adigital document are editable, and how editing the elements affects thedigital document. This causes such system resources to be less availableor unavailable for other computing tasks. Thus, techniques utilized byconventional content creation systems for enabling digital documents tobe generated and edited are inefficient both from a user workflowperspective, and from a system resources perspective.

SUMMARY

To overcome these problems, techniques for generating edit suggestionsfor transforming digital documents are implemented in a digital mediumenvironment. For instance, a user leverages a content editor applicationto retrieve a digital document for editing, such as a web page. Thecontent editor application parses the digital document to extract adigital page, and page elements of the digital page that are editable.The content editor application then outputs a graphical user interface(GUI) that identifies the page elements that are editable. The GUI, forinstance, includes a suggestions menu with different edit suggestionsthat each correlate to different respective page elements. A user maythen interact with individual edit suggestions to edit the differentpage elements, such as by adding, removing, or revising digital contentof the page elements. The described techniques, for example,automatically identify editable page elements of a digital page, andoutput edit suggestions for editing the page elements without requiringuser selection of the page elements or even user knowledge of which pageelements are editable.

This Summary introduces a selection of concepts in a simplified formthat are further described below in the Detailed Description. As such,this Summary is not intended to identify essential features of theclaimed subject matter, nor is it intended to be used as an aid indetermining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ techniques described herein.

FIG. 2 depicts portions of a content editor system which enablesdifferent user experiences to be generated utilizing techniques forgenerating edit suggestions for transforming digital documents describedherein.

FIG. 3 depicts a scenario for initiating an edit mode for editing adigital document.

FIG. 4 depicts a scenario for selection of a particular element forediting.

FIG. 5 depicts a scenario for applying edits to an element of a digitaldocument.

FIG. 6 depicts a scenario for selection of a particular element forediting.

FIG. 7 depicts a scenario for applying edits to an element of a digitaldocument.

FIG. 8 depicts a scenario for tracking changes to a digital document.

FIG. 9 depicts an example procedure for transforming a digital documentbased on an edit suggestion.

FIG. 10 depicts an example procedure for generating an editrecommendation for a digital document based on historical performancedata.

FIG. 11 depicts an example procedure for logging edits to a digitaldocument.

FIG. 12 illustrates an example system including various components of anexample device that can be implemented as any type of computing deviceas described and/or utilized with reference to FIGS. 1-11 to implementembodiments of the techniques described herein.

DETAILED DESCRIPTION

Overview

Conventional content editing systems that provide digital documentediting functionality typically enable a user to apply various edits toa digital document to generate an edited version of the digitaldocument. Such conventional systems, however, do not typically providefunctionality for efficiently and intuitively demonstrating how adigital document is editable. Thus, conventional content editing systemsare burdensome on user and system resources by requiring extensive userinteraction to discover how a particular digital document is editable,and to apply edits to the digital document. Further, by requiringextensive manual user interaction to edit digital documents, suchconventional systems prevent system resources (e.g., processor andmemory bandwidth) allocated to the manual processes from being availablefor other system tasks.

To overcome these drawbacks with conventional content editing systems,techniques for generating edit suggestions for transforming digitaldocuments are implemented in a digital medium environment. For instance,a user leverages a content editor application to retrieve a digitaldocument for editing, such as a web page. The content editor applicationparses the digital document to extract a digital page, and page elementsof the digital page that are editable. The content editor applicationthen outputs a graphical user interface (GUI) that identifies the pageelements that are editable. The GUI, for instance, includes asuggestions menu with different edit suggestions that each correlate todifferent respective page elements. A user may then interact withindividual edit suggestions to edit the different page elements, such asby adding, removing, or revising digital content of the page elements.In at least some implementations, the edit suggestions are presented asinteractive objects separately from the page elements, and a user mayedit the page elements via interaction with the edit suggestions andwithout interacting directly with the page elements. Generally,techniques described herein can automatically identify editable pageelements of a digital page and output edit suggestions for editing thepage elements without requiring user selection of the page elements oreven user knowledge of which page elements are editable.

Further, the described techniques provide recommendations for ways inwhich to edit page elements, such as page elements identified as part ofa set of editable page elements. For instance, when a particular edit isapplied to a digital document and the digital document is published,performance of the digital document is monitored to generate performancedata that indicates how the digital document performs over a period oftime. Generally, “performance” is measurable based on quantities of userinteractions with the digital document, such as user accesses,purchases, registrations, recommendations, and so forth, pertaining to adigital document. The performance data can then be used to generaterecommendations of ways for editing other digital documents. Forexample, consider that after the digital document was edited andpublished, performance of the digital document was observed to increase.The increase in performance can be attributed to the particular edit,and thus the edit can be recommended for other digital documents. Forinstance, when a user interacts with a content editor application toedit a digital document, the content editor application can present theedit as a recommendation for editing the digital document.

In this way, techniques for generating edit suggestions for transformingdigital documents provide automated processes for generating andoutputting edit suggestions that present different ways for editing andtransforming digital documents. By providing automated identification ofeditable page elements and outputting interactive edit suggestions forthe page elements, the disclosed techniques greatly reduce the number ofuser interactions and system resources required to enable digitaldocument editing in comparison with conventional content editingsystems. Thus, a more efficient content editor experience is providedthat conserves system resources as well as user time and interactionrequired to discover ways for editing digital documents.

Term Descriptions

These term descriptions are provided for purposes of example only andare not intended to be construed as limiting on the scope of the claims.

As used herein, the term “digital document” refers to digitalcollections of digital content, such as generated using images, text,animations, videos, audio, and so forth. Examples of digital documentsinclude markup-based documents such as websites and web platforms forvarious purposes such as eCommerce, social media, education, governmententities, and so forth. A digital document can be published for accessin different ways, such as by an online content platform that publishesdigital documents for online access over the Internet.

As used herein, the term “digital page” refers to a portion of a digitaldocument, such as a web page of a website. In at least someimplementations, a digital document can be made up of multiple digitalpages, and each digital page can be populated with different types andinstances of digital content. For instance, a website includes differenttypes of digital pages such as a home page, a directory page, a productpage, a contact page, and so forth.

As used herein, the term “page type” refers to a classification of adigital page. For instance, different page types are defined fordifferent digital pages, such as based on a purpose of a digital pagewithin a digital document, and/or a type of digital content included ina digital page. Examples of different page types include a “home page”which represents an initial and/or main page of a digital document, a“directory page” that identifies different instances and categories ofdigital pages of a digital document (e.g., which includes links to otherdigital pages of the digital document), a “product page” which includesdigital content pertaining to a product offered by a digital document, a“contact page” which enables a user to initiate contact with an entityassociated with a digital document, and so forth.

As used herein, the term “page element” refers to different digitalconstructs that make up a digital page. A page element, for instance,can be populated with digital content to form a digital page. Examplesof page elements include bounding boxes, controls, Tillable fields,menus, and so forth. Generally, a user can generate and edit a digitalpage by arranging different page elements on the digital page, andinserting and/or editing digital content for the individual pageelements.

As used herein, the term “content platform” refers to network-basedentities that publish digital documents. Examples of content platformsinclude eCommerce platforms (e.g., Magento®, Shopify®), social mediaplatforms (e.g., Facebook®, Twitter®), educational platforms (e.g.,Udemy®), and so forth. A user, for instance, can generate and edit adigital document, and provide the digital document to a contentplatform. The content platform can then publish the digital document foraccess by different users, such as via the Internet.

As used herein, the term “edit suggestion” refers to indications ofdifferent page elements that are editable. For instance, different pageelements of a digital page can be extracted and identified (e.g.,visually emphasized) using edit suggestions that indicate that the pageelements are editable. In at least some implementations, an editsuggestion represents a visual interactive object that is able toreceive user input to edit a respective page element represented by theedit suggestion.

As used herein, the term “edit interaction” refers to interactions withpage elements to edit the page elements, such as by adding or removingdigital content, and/or revising existing digital content. An editinteraction, for example, is based on user input to a content editorapplication to edit digital content included in page elements of adigital page.

As used herein, the term “edit recommendation” refers to a recommendedway for editing a page element. An edit recommendation, for instance,includes plain text guidance for editing a page element, and is specificto a particular page element. As used herein, for example, an editsuggestion identifies a page element that is editable, and an editrecommendation provides guidance for editing the page element.

As used herein, the term “performance data” refers to data thatdescribes how a particular digital document and/or digital page performsin an online environment, such as over the Internet. Examples ofperformance data include a number of user accesses, purchases,registrations, recommendations, and so forth, pertaining to a digitaldocument and/or a digital page. In at least some implementations,performance data can be dated to indicate performance and changes inperformance over specific periods of time.

In the following discussion, an example environment is first describedthat may employ the techniques described herein. Example implementationdetails and procedures are then described which may be performed in theexample environment as well as other environments. Consequently,performance of the example procedures is not limited to the exampleenvironment and the example environment is not limited to performance ofthe example procedures.

Example Environment

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ techniques for generating editsuggestions for transforming digital documents described herein. Theillustrated environment 100 includes a client device 102, a contenteditor service system (“content editor service”) 104, and contentplatforms 106 that are communicatively coupled, one to another, vianetworks 108.

Computing devices that are usable to implement the client device 102,the content editor service 104, and the content platforms 106 may beconfigured in a variety of ways, such as a desktop computer, a laptopcomputer, a mobile device (e.g., assuming a handheld configuration suchas a tablet or mobile phone), a server device, and so forth.Additionally, a computing device may be representative of a plurality ofdifferent devices, such as multiple servers utilized to performoperations via a network-based service (e.g., “over the cloud”) asfurther described in relation to FIG. 12.

The client device 102 includes a content editor application 110 that isrepresentative of functionality to perform various editing interactionswith digital documents, such as for generating and editing digitaldocuments. Further to techniques described herein, the content editorapplication 110 maintains application data 112 stored on a local storage114 and which includes digital documents 116, platform data 118,suggestion data 120, and historical data 122. The digital documents 116are representative of various collections of digital content, and may beimplemented in a variety of different digital content formats.Generally, the digital documents 116 may take various forms, such aswebsites, web applications, social media pages, and so forth.

The digital documents 116 include digital pages 124, page elements 126,and digital content 128 which are leveraged to generate differentinstances of the digital documents 116. The pages 124, for instance,represent different divisions of a digital document 116, such as webpages of a website, pages of a multimedia document, posts to a socialmedia platform, and so forth. The page elements 126 represent differentvisual and functional elements of the digital documents 116, such asbanners, menus, functional controls (e.g., selectable buttons), contentcontainers, search fields, and so forth. The page elements 126, forexample, represent different visual features used to generate the pages124.

In at least some implementations, the page elements 126 are arrangedinto different categories to facilitate editing of the page elementsaccording to techniques for generating edit suggestions for transformingdigital documents. The categories, for instance, represent differenttypes of page elements 126, such as “page banner,” “menu,” “control,”“container,” “search field,” and so forth. Further, different types ofpage elements 126 can be associated with different types of the digitalpages 124. Examples of different types of digital pages 124 include“home page,” “product page,” “registration page,” “contact page,” and soforth. Generally, different types of page elements 126 can be associatedwith different types of digital pages 124, which facilitatesidentification of page elements 126 for purposes of editing the pageelements.

The digital content 128 represents content that can be populated to theelements 126 and the pages 124 as part of generating and editing thedigital documents 116. Examples of the digital content 128 includeimages, text, audio, video, multimedia, and so on. Generally, thecontent editor application 110 enables the digital content 128 to bemanipulated in various ways to generate and edit the digital documents116.

The suggestion data 120 represents data that can be leveraged by thecontent editor application 110 to suggest different ways in which adigital document 116 can be created and edited. For instance, thesuggestion data 120 includes data that can be output by the contenteditor application 110 to provide suggestions and recommendations tousers regarding ways in which the digital content 128 can be manipulatedto edit instances of the digital documents 116.

The platform data 118 represents data that is usable to identify anddifferentiate the different content platforms 106. As further describedbelow, certain of the content platforms 106 can have platform-specificattributes that can be leveraged to determine ways in which digitaldocuments served by the content platforms 106 can be generated andedited. The platform data 118, for instance, includes metadata (e.g.,meta tags) that can be matched to attributes of a digital document toidentify a content platform 106 that publishes the digital document.

The historical data 122 represents data that tracks different historicalattributes of the digital documents 116 and the digital content 128. Forinstance, the historical data 122 tracks historical performance andmetrics of the digital documents 116, such as a number of onlineaccesses over a period of time, a number of product sales resulting frominstances of the digital documents 116, user feedback regardinginstances of the digital documents 116, a number of click-throughsoccurring from a digital document 116, user sentiment regarding thedigital documents, and so forth. In at least some implementations, thehistorical data 122 can be leveraged to generate the suggestion data120. For instance, if the historical data 122 indicates that aparticular edit applied to the digital content 128 caused an increase inperformance of a digital document 116, the suggestion data 120 can beconfigured generate a recommendation to apply a similar edit to anotherinstance of a digital document 116.

Further to techniques for generating edit suggestions for transformingdigital documents, the content editor application 110 includes aplatform identification module 130, a page identification module 132, anelement identification module 134, and a suggestion module 136 that eachprovide different aspects of the functionality described herein. Theplatform identification module 130, for instance, representsfunctionality for identifying which of the content platforms 106 aparticular digital document 116 is associated with. To correlate aparticular digital document with a content platform 106, the platformidentification module 130 can leverage the platform data 118 to matchknown digital document attributes (e.g., metadata) for a contentplatform 106 to attributes of the digital document.

In at least some implementations, digital documents 116 that aregenerated and edited by the content editor application 110 can be servedto different users by the content platforms 106. Generally, the contentplatforms 106 represent different online platforms such as websites,social media platforms, eCommerce platforms, and so forth. The contentplatforms 106, for example, publish digital documents 116 which includeinstances of the digital documents 116 generated and/or edited by thecontent editor application 110. For instance, the client device 102retrieves an instance of a digital document 116 from a content platform106, edits the digital document 116 to generate an edited instance of adigital document 116, and then communicates the edited digital document116 to the content platform 106 for publishing.

The page identification module 132 represents functionality foridentifying different page types for the pages 124. Examples ofdifferent page types that the page identification module 132 is able toidentify include home pages of a website, product pages of an eCommerceplatform, custom page types identified for different online platforms,and so forth. The element identification module 134 representsfunctionality for identifying different element types for the elements126, examples of which are discussed above.

The suggestion module 136 represents functionality for generating andexposing the suggestion data 120. For instance, the suggestion module136 can generate the suggestion data 120 (e.g., based on the historicaldata 122), and can output the suggestion data 120 to suggest differentways in which the digital documents 116 can be edited. As furtherdescribed below, the suggestion module 136 can output the suggestiondata 120 based on different attributes of the digital documents 116,such as page types identified by the page identification module 132,element types identified by the element identification module 134, andso forth.

To enable users to interact with the content editor application 110, thecontent editor application 110 includes a content editor graphical userinterface (“GUI”) 138 displayed on display device 140 of the clientdevice 102. The content editor GUI 138 is representative offunctionality to present various visual affordances and user experiencesas part of interacting with the content editor application 110.

In at least some implementations, certain content editing actions anduser experiences of the content editor application 110 can be performedin part or wholly by the content editor service 104. The content editorservice 104, for example, represents a network-based service that canassist the client device 102 in performing various content editingactions via the content editor application 110. To enable the contenteditor service 104 to perform such actions, the content editor service104 maintains a service manager module 142 and service data 144 storedon a system storage 146. Generally, the service manager module 142 isrepresentative of functionality for performing actions as part oftechniques for generating edit suggestions for transforming digitaldocuments described herein. For instance, the various interactions anduser experiences described herein can be implemented at the clientdevice 102, the content editor service 104, and/or via interactionbetween the client device 102 and the content editor service 104 overthe networks 108. Further, the various data stored on the local storage114 of the client device 102 may additionally or alternatively be storedas part of the service data 144 for access by the content editor service104 and/or the client device 102.

FIG. 2 depicts portions of a content editor system 200 in an exampleimplementation for transforming a digital document utilizing techniquesdescribed herein. In the system 200, the content editor application 110obtains a digital document 116 from a content platform 106. A user, forinstance, interacts with the content editor application 110 to provideinput to retrieve the digital document 116 from the content platform106. Alternatively or additionally, the digital document 116 is storedon the client device 102 and the user retrieves the digital document 116from the local storage 114. The digital document 116 includes a digitalpage 124 with page elements 126 and digital content 128.

The platform identification module 130 then processes the digitaldocument 116 to determine a platform identifier (“ID”) 202 thatidentifies the content platform 106. For instance, the platformidentification module 130 utilizes the platform data 118 to inspect data(e.g., metadata) of the digital document 116, and match the data to aknown data signature of the content platform 106 to ascertain theplatform ID 202. The page identification module 132 then inspects thedigital page 124 of the digital document 116 to determine a page type204 for the digital page 124. In at least some implementations, the pageidentification module 132 leverages the platform data 118 to determinepage types utilized by the content platform 106. Generally, differentpage types may affect how edits to the digital document 116 aresuggested and/or applied.

Continuing, the element identification module 134 processes the pageelements 126 of the digital page 124 to determine different elementtypes 206 for the elements 126. The suggestion module 136 then generatesedit suggestions 208 based on the platform ID 202, the page type 204,and element types 206. The edit suggestions 208, for example, are outputvia the content editor GUI 138. Generally, the edit suggestions 208identify particular pages 124, elements 126, and/or digital content 128that are editable to transform the digital document 116. As furtherdetailed below, the edit suggestions 208 can be presented as interactivevisual objects that are configured to receive user input to edit thedigital content 128 populated to the various elements 126 of the digitaldocument 116.

In at least some implementations, the suggestion module 136 leveragesthe suggestion data 120 and the historical data 122 to generate the editsuggestions 208. The suggestion data 120, for example, includes datadescribing different ways in which attributes of the digital document116 are editable, such as the page 124, the elements 126, and/or thedigital content 128. Further, the historical data 122 indicatesperformance-related data for previous ways in which digital documentswere edited, such as how different types of edits affected performanceof instances of digital documents. The suggestion module 136, forexample, can recommend edits that have been historically observed ashaving contributed to an increase in performance of digital documents.

Based on the edit suggestions 208, a user performs edit operations 210to the digital document 116 to generate an edited digital document 212.The edited digital document 212, for example, represents an editedinstance of the digital document 116. The edited digital document 212 isthen communicated to a content platform 106 for publishing.

Thus, as depicted in the system 200, techniques for generating editsuggestions for transforming digital documents can be employed toprovide edit suggestions for editing digital documents, and to enabledigital documents to be transformed by edits applied based on the editsuggestions.

FIGS. 3-8 depict aspects of example scenarios for generating editsuggestions for transforming digital documents. For instance, FIG. 3depicts a scenario 300 for initiating an edit mode for editing a digitaldocument. In the scenario 300, a web page 302 is displayed on thecontent editor GUI 138 of the content editor application 110. Generally,the web page 302 represents an instance of a digital document 116. In atleast one implementation, the web page 302 is displayed in response to auser interacting with the client device 102 to retrieve the web page 124from a particular content platform 106.

The content editor application 110 processes the web page 302 toidentify edit suggestions 208 that represent different attributes of theweb page 302 that are editable. One example way of processing a digitaldocument to identify edit suggestions is discussed above with referenceto the scenario 200. Accordingly, the content editor application 110presents an edit prompt 304 that identifies a content platform 106 thatpublishes the page (“Platform ABC”) and a page type 204 for the page,“eCommerce Product Page.” The edit prompt 304 also includes an editsuggestion control 306 that is selectable to initiate an edit mode forediting the web page 302.

Accordingly, based on selection of the suggestion control 306, an editmode 308 is activated that enables the web page 302 to be edited viainteraction with the content editor application 110. In at least oneimplementation, before the edit mode 308 is activated, an authenticationprocess is performed to determine whether a particular user isauthorized to edit the web page 302. Thus, the edit mode 308 can beactivated based on a successful authentication.

In the edit mode 308, different editable elements 310 of the web page302 are identified as being editable. The editable elements 310 aredepicted as surrounded by dashed lines providing a visual indicationthat the elements are editable. Further, the editable elements 310 arelabeled to differentiate from one another, such as using a differentnumber for each editable element. An edit suggestions menu 312 is alsopresented, which lists different edit suggestions 208 based on theidentified editable elements. For instance, individual editable elements310 each include a different respective edit suggestion 208 listed inthe suggestions menu 312. Generally, each edit suggestion 208 includedin the suggestions menu 312 identifies a different editable element 310and an action that can be applied to the editable element, e.g.,“change” the editable element.

FIG. 4 depicts a scenario 400 for selection of a particular element forediting. The scenario 400, for example, represents a continuation of thescenario 300 as part of the edit mode 308. In the scenario 400, a userselects a change price description option 402 from the suggestions menu312 to enable an element 404 of the editable elements 310 to be edited.Based on selection of the option 402, an element editing menu 406 ispresented that includes various information and editing options for theelement 404. The element editing menu 406, for instance, includes anaction field 408, an element name field 410, a content field 412, and arecommendation field 414. The action field 408 generally identifies anedit-related action that is available for editing the element 404, whichin this example indicates that price description for a product presentedin the web page 302 is editable. The element name field 410 identifies aname for the element 404. In at least some implementations, the namepresented in the element name field 410 can be based on a writtenlanguage and/or a markup language, such as Cascading Style Sheets (CSS).

The content field 412 includes content that is populated to the element404, as well as attributes of the content. In this particular example,the content field 412 includes digital text content from the element404, as well as attributes of the text content, e.g., font attributes.While this scenario is discussed with reference to text content, it isto be appreciated that various other types of digital content can bepopulated to the content field 412, such as images, video, audio, and soforth.

The recommendation field 414 includes recommendations for how to editthe element 404, such as particular ways to perform the actionidentified in the action field 408. In at least one implementation, therecommendation field 414 is populated based on information fromsuggestion data 120, which in turn can be generated based on thehistorical data 122. For instance, the historical data 122 indicatesdifferent historical performance statistics for changes made to productprice fields of different digital documents 116, such as the effect ofcharacterizing the product price in different ways on performance ofrespective digital documents. Thus, the recommendation field 414 can bepopulated with guidance for changing the element 404 that ishistorically indicated as leading to an increase in performance ofsimilar digital documents.

FIG. 5 depicts a scenario 500 for applying edits to an element of adigital document. The scenario 500, for example, represents acontinuation of the scenarios 300, 400 as part of the edit mode 308. Inthe scenario 500, a user provides input 502 to change the contentincluded in the element 404, such as by editing the content viainteraction with the content field 412 and/or the element 404 itself.The user then selects a save control 504, which causes the changes tothe element 404 to be saved to generate an edited element 506.Accordingly, the element 404 is transformed via the user input 502 togenerate an edited web page 508, which represents a modified version ofthe web page 302. The element editing menu 406 also includes a cancelcontrol 510 that is selectable to cancel editing of the element 404,such as to cause the element editing menu 406 to be removed fromdisplay. Continuing, after the element 404 is edited, the suggestionsmenu 312 is presented to enable other elements of the edited web page508 to be edited.

FIG. 6 depicts a scenario 600 for selection of a particular element forediting. The scenario 600, for example, represents a continuation of thescenarios 300-500 as part of the edit mode 308. In the scenario 600, theedited web page 508 is displayed in the content editor GUI 138 alongwith the suggestions menu 312.

Continuing, a user selects an edit suggestion 208 in the form of achange banner option 602 from the suggestions menu 312 to enable anelement 604 (e.g., a website banner) of the editable elements 310 to beedited. Based on selection of the change banner option 602, an elementediting menu 606 is presented that includes various information andediting options for the element 604. The element editing menu 406, forinstance, includes the action field 408, the element name field 410, thecontent field 412, and the recommendation field 414. Example attributesof these fields are discussed above with reference to the scenario 400.In this particular example, the recommendation field 414 recommendschanging a font of the content included in the element 604, e.g., thewebsite banner.

FIG. 7 depicts a scenario 700 for applying edits to an element of adigital document. The scenario 700, for example, represents acontinuation of the scenarios 300-600 as part of the edit mode 308. Inthe scenario 700, a user provides input 702 to change the contentincluded in the element 604. The user, for instance, interacts with thecontent field 412 of the editing menu 606 to change the font used forthe content of the element 604. The user then selects the save control504 which causes the edits to the element 604 to be saved to generate afurther edited web page 704, which represents an edited version of theedited web page 508.

In at least some implementations, the various editing interactionsdescribed in the scenarios above are performed on a version of theoriginal web page 302 that is offline for editing, e.g., not “live.”Accordingly, the user selects an apply control 706 from the suggestionsmenu 312, which causes the edited web page 704 to be published online,such as for general access via the content platform 106 from which theweb page 302 was previously retrieved. The web page 302, for example, isreplaced at the content platform 106 with the edited web page 704 suchthat users can access the edited web page 704 via interaction with thecontent platform, such as over the Internet.

FIG. 8 depicts a scenario 800 for tracking changes to a digitaldocument. The scenario 800, for example, represents a way of trackingand presenting the web page edits described above, and thus can beimplemented in conjunction with the scenarios presented above. Thescenario 800 includes a change log interface 802 displayed within thecontent editor GUI 138. Generally, the change log interface 802 includesinformation about various changes made to a digital document 804. Thedigital document 804, for example represents an instance of the digitaldocuments 116, such as the web page 302 and/or the edited web page 704.

In this particular example, the change log interface 802 includes a pageidentification field 806 that identifies the digital document 804 forwhich changes are presented in the change log interface 802. The changelog interface 802 also includes a changes region 808 that identifies thevarious changes previously made to the digital document 804. The changesregion 808, for example, includes an action column that identifies anelement and an action applied to the element, a status column thatindicates whether a particular change was successful, a user column thatidentifies a user that applied a respective change, and a date columnthat indicates a date on which a respective change was applied to thedigital document 804. Each entry in the changes region 808 also includesa details control that is selectable to view additional detailsregarding a respective entry in the changes region 808.

Further to the scenario 800, a user selects a details control 810 from alog entry 812 of the changes region 808. Accordingly, a detailsinterface 814 is presented that includes details about the log entry812. The details interface 814, for example, includes a details field816 and a performance stats field 818. The details field 816 identifiesthe various changes made to an element of the digital document 804.Further, the performance stats field 818 includes statistics regardingthe digital document 804 based on the change to the digital document 804represented by the log entry 812. The information in the performancestats field 818, for instance, represent different performance-relatedstatistics for the digital document 804 over a particular time periodafter the change to the digital document 804 represented by the logentry 812 was applied. In at least one implementation, informationpopulated to the performance stats field 818 is retrieved from thehistorical data 122 for the digital document 804.

The details interface 814 includes a done control 820 that is selectableto return to the change log interface 802, and an edit page control 822that is selectable to edit the page of the digital document 804represented by the change log interface 802. For instance, selecting theedit page control 822 can transition the digital document 804 into anedit mode, such as described in the scenarios above. In at least oneimplementation, selecting the edit page control 822 presents an elementof the digital document 804 for editing, e.g., the “product price”element represented by the details interface 814.

Accordingly, the various scenarios described above illustrate thattechniques for generating edit suggestions for transforming digitaldocuments can be employed to provide simple and intuitive ways to enableusers to transform digital documents in different ways.

FIG. 9 depicts an example procedure 900 for transforming a digitaldocument based on an edit suggestion. A digital document is processed toidentify a content platform that publishes the digital document (block902). A user, for instance, interacts with the content editorapplication 110 to obtain a digital document 116, such as from a contentplatform 106. The platform identification module 130 then parses thecode of a digital document 116 to identify a content platform 106 thatis a source of the digital document 116. A tag included in the code(e.g., a metatag), for example, can be identified that specifies a namefor a particular content platform 106.

Code of the digital document is processed to identify data embedded inthe code that identifies a page type for a digital page of the digitaldocument (block 904). In at least one implementation, the code includesa Document Object Model (DOM) for the digital document. For example,based on the identified content platform, a page type for a particularpage 124 to be edited is identified. The page identification module 132,for instance, parses code of a page 124 of the digital document 116 toidentify a page type for the page 124. In at least some implementations,different content platforms 106 utilize different page types that can bespecific to the content platforms. For instance, the content platforms106 expose metatags and/or library functions in their respective digitaldocuments 116 that identify specific page types in the digitaldocuments. The following represents example function that can beutilized to determine a page type of a page 124 of a digital document116:

Function 1—Platform and Page Identification

-   -   # For a given platform P    -   # check if platform is known set of platforms    -   # If yes, extract page type from the metadata or variable        corresponding to platform. Example:        window.google_tag_params.ecomm_pagetype;    -   # If not use standard way of extracting meta tags from HTML page        and deduce the page type.

As illustrated in Function 1, different page types can be mapped andidentified based on the different content platforms.

A set of editable page elements are extracted from the digital page(block 906). The element identification module 134, for example, matchespage elements embedded in the code of the digital page to categories ofeditable page elements identified based on the page type. Generally,different categories of page elements that are available to be editedcan be specified, and can be used to ascertain which page elements of aparticular page are editable via the content editor application 110. Thefollowing represents example function that can be utilized to determineelement types for elements 126 of a page 124 of a digital document 116:

Function 2—Element Identification

-   -   # Input: Page type, Assumption: expected Elements for Page type.    -   # Parse the page to identify major content containers in page.        Like header, footer, product content.    -   # Scan the elements of each container, to find each of the        expected element.    -   # For Image, parse page to get all images. Identify the image        with prominent height and width in container and mark as product        Image. Further use attribute like title, class while determining        the probability of it being product image.    -   # For price, extract all numeric values with unit of price like        99.9 $.    -   # For title, look above identified product image and price        elements. Also, title attributes have specific element type like        Heading, Label etc.

Generally, the pseudo code for element identification included inFunction 2 depends on page type identified earlier in Function 1 anduses heuristics to identify expected page elements. In the examplescenarios described above, the page type is “Product Page,” so examplesof the expected page elements are Price, Product Image, and ProductTitle.

Visual representations of the editable page elements are generated thateach include an edit suggestion for editing an editable page element(block 908). The suggestion module 136, for example, generates differentedit suggestions based on the types of editable page elements. In atleast some implementations, the suggestion data 120 includes instancesof edit suggestions that are each specific to a type of editable pageelement. Thus, the suggestion module 136 can retrieve edit suggestionsby mapping elements types for the editable page elements to respectiveedit suggestions in the suggestion data 120.

Using the edit suggestions, a GUI is rendered that includes the digitaldocument with the editable page elements, and visual representations ofthe editable page elements displayed separately from the digitaldocument. Generally, the visual representations each including an editsuggestion for editing a respective page element of the editable pageelements. Examples of the GUI and the visual representations arediscussed above with reference to the content editor GUI 138 and thesuggestions menu 312, respectively.

An edit interaction is received to a particular visual representation ofan editable page element indicating an edit to be applied to theeditable page element (block 910). A user, for instance, interacts witha particular visual representation of an editable page element (e.g., inthe suggestions menu 312) to enable editing of a respective editablepage element. In at least one implementation, a user selects an editsuggestion from the suggestions menu 312, which causes an elementediting menu to be presented. The user can then interact with theelement editing menu to provide edits to the editable page element, suchas to modify digital content of the editable page element. Alternativelyor in addition, the user can interact with the editable page elementitself to edit the page element.

The digital document is transformed by modifying the editable pageelement based on the edit interaction (block 912). The content editorapplication 110, for example, applies the edit to the editable pageelement to transform the digital document and generate an edited versionof the digital document. The client device 102 then communicates theedited digital document to a particular content platform 106 forpublishing, such as the content platform 106 from which the digitaldocument was originally obtained for editing.

FIG. 10 depicts an example procedure 1000 for generating an editrecommendation for a digital document based on historical performancedata. An edit is applied to a digital document to generate an editeddigital document (block 1002). A user, for instance, interacts with thecontent editor application 110 to apply an edit to a digital documentand generate an edited digital document, such as described withreference to the procedure 900. Editing the digital document, forinstance, includes modifying digital content of a page element of thedigital document.

The edited digital document is caused to be published (block 1004). Theedited digital document 116, for example, is communicated to a contentplatform 106, which publishes the edited digital document. Generally,this enables different users to access the edited digital document, suchas via the networks 108.

Performance data for the edited digital document is retrieved (block1006). The content editor application 110, for example, retrievesperformance data for the edited digital document from the contentplatform 106 that publishes the edited digital document. For instance,after the content platform 106 receives and publishes the edited digitaldocument, the content platform 106 tracks various performance-relatedstatistics for the edited digital document, such as numbers of userinteractions with the edited digital document. Examples of such userinteractions include user visits to the edited digital document, userpurchases via the edited digital document, user registrations via theedited digital document, user sentiment expressed regarding the editeddigital document (e.g., favorable and unfavorable sentiments), and soforth. The content platform 106 then provides the performance data tothe client device 102 for receipt by the content editor application 110.

The performance data is analyzed to determine performance attributes ofthe edited digital document (block 1008). The content editor application110, for instance, processes the performance data to identifyperformance trends over a period of time, such as increases or decreasesin user interactions with the edited digital document over a discreteperiod of time.

An edit recommendation is generated by correlating the performanceattributes to the edit applied to the digital document (block 1010). Forexample, the content editor application 110 generates an editrecommendation that indicates that the edited digital document performeda particular way after the edit was applied to the digital document. Theedit recommendation, for instance, may indicate that performance of thedigital document increased or decreased after the edit was applied andthe edited digital document was published. In at least someimplementations, the edit recommendation is generated as a plain texthuman-readable statement that is stored as part of the suggestion data120 and that can be displayed by the content editor application 110 aspart of editing a different digital document.

FIG. 11 depicts an example procedure 1100 for logging edits to a digitaldocument. Edits to a digital document are received (block 1102). A user,for instance, interacts with the content editor application 110 to applyedits to a digital document, such as described above. The edits arelogged using descriptions of the edits over time (block 1104). Thecontent editor application 110, for example, generates a change log foreach edit that includes a plain text description of the edit, an author,a date, and so forth.

A graphical user interface (GUI) is rendered that includes change logswith the descriptions of the edits over time (block 1106). The contenteditor application 110, for example, generates the change log interface802 that identifies various edits made to a digital document over time.In at least one implementation, the GUI is rendered to include furtherdetails about particular edits, such as described with reference to thescenario 800.

Accordingly, techniques for generating edit suggestions for transformingdigital documents provide efficient and intuitive ways for guiding usersthrough editing processes for editing and publishing digital documents.

Discussed above are a number of procedures. Aspects of the proceduresdescribed herein may be implemented in hardware, firmware, or software,or a combination thereof. The procedures are shown as a set of blocksthat specify operations performed by one or more devices and are notnecessarily limited to the orders shown for performing the operations bythe respective blocks. In at least some implementations the proceduresare performed by a suitably configured device, such as the client device102, the content editor service 104, and/or via cooperation between theclient device 102 and the content editor service 104.

Having described example scenarios and procedures in accordance with oneor more implementations, consider now an example system and device thatcan be utilized to implement the various techniques described herein.

Example System and Device

FIG. 12 illustrates an example system generally at 1200 that includes anexample computing device 1202 that is representative of one or morecomputing systems and/or devices that may implement the varioustechniques described herein. This is illustrated through inclusion ofthe content editor application 110 and the service manager module 142.The computing device 1202 may be, for example, a server of a serviceprovider, a device associated with a client (e.g., a client device), anon-chip system, and/or any other suitable computing device or computingsystem.

The example computing device 1202 as illustrated includes a processingsystem 1204, one or more computer-readable media 1206, and one or moreI/O interfaces 1208 that are communicatively coupled, one to another.Although not shown, the computing device 1202 may further include asystem bus or other data and command transfer system that couples thevarious components, one to another. A system bus can include any one orcombination of different bus structures, such as a memory bus or memorycontroller, a peripheral bus, a universal serial bus, and/or a processoror local bus that utilizes any of a variety of bus architectures. Avariety of other examples are also contemplated, such as control anddata lines.

The processing system 1204 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 1204 is illustrated as including hardware elements 1210 that maybe configured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 1210 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable storage media 1206 is illustrated as includingmemory/storage 1212. The memory/storage 1212 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage component 1212 may include volatile media (such as randomaccess memory (RAM)) and/or nonvolatile media (such as read only memory(ROM), Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage component 1212 may include fixed media (e.g., RAM, ROM, afixed hard drive, and so on) as well as removable media (e.g., Flashmemory, a removable hard drive, an optical disc, and so forth). Thecomputer-readable media 1206 may be configured in a variety of otherways as further described below.

Input/output interface(s) 1208 are representative of functionality toallow a user to enter commands and information to computing device 1202,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone, a scanner, touch functionality (e.g., capacitiveor other sensors that are configured to detect physical touch), a camera(e.g., which may employ visible or non-visible wavelengths such asinfrared frequencies to recognize movement as gestures that do notinvolve touch), and so forth. Examples of output devices include adisplay device (e.g., a monitor or projector), speakers, a printer, anetwork card, tactile-response device, and so forth. Thus, the computingdevice 1202 may be configured in a variety of ways as further describedbelow to support user interaction.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,” and“component” as used herein generally represent software, firmware,hardware, or a combination thereof. The features of the techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 1202. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent and/or non-transitory storage of information incontrast to mere signal transmission, carrier waves, or signals per se.Computer-readable storage media do not include signals per se. Thecomputer-readable storage media includes hardware such as volatile andnon-volatile, removable and non-removable media and/or storage devicesimplemented in a method or technology suitable for storage ofinformation such as computer readable instructions, data structures,program modules, logic elements/circuits, or other data. Examples ofcomputer-readable storage media may include, but are not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM,digital versatile disks (DVD) or other optical storage, hard disks,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other storage device, tangible media, orarticle of manufacture suitable to store the desired information andwhich may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 1202, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared, and other wireless media. [oioi] As previouslydescribed, hardware elements 1210 and computer-readable media 1206 arerepresentative of modules, programmable device logic and/or fixed devicelogic implemented in a hardware form that may be employed in someembodiments to implement at least some aspects of the techniquesdescribed herein, such as to perform one or more instructions. Hardwaremay include components of an integrated circuit or on-chip system, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), a complex programmable logic device (CPLD), and otherimplementations in silicon or other hardware. In this context, hardwaremay operate as a processing device that performs program tasks definedby instructions and/or logic embodied by the hardware as well as ahardware utilized to store instructions for execution, e.g., thecomputer-readable storage media described previously.

Combinations of the foregoing may also be employed to implement varioustechniques described herein. Accordingly, software, hardware, orexecutable modules may be implemented as one or more instructions and/orlogic embodied on some form of computer-readable storage media and/or byone or more hardware elements 1210. The computing device 1202 may beconfigured to implement particular instructions and/or functionscorresponding to the software and/or hardware modules. Accordingly,implementation of a module that is executable by the computing device1202 as software may be achieved at least partially in hardware, e.g.,through use of computer-readable storage media and/or hardware elements1210 of the processing system 1204. The instructions and/or functionsmay be executable/operable by one or more articles of manufacture (forexample, one or more computing devices 1202 and/or processing systems1204) to implement techniques, modules, and examples described herein.

The techniques described herein may be supported by variousconfigurations of the computing device 1202 and are not limited to thespecific examples of the techniques described herein. This functionalitymay also be implemented all or in part through use of a distributedsystem, such as over a “cloud” 1214 via a platform 1216 as describedbelow.

The cloud 1214 includes and/or is representative of a platform 1216 forresources 1218. The platform 1216 abstracts underlying functionality ofhardware (e.g., servers) and software resources of the cloud 1214. Theresources 1218 may include applications and/or data that can be utilizedwhile computer processing is executed on servers that are remote fromthe computing device 1202. Resources 1218 can also include servicesprovided over the Internet and/or through a subscriber network, such asa cellular or Wi-Fi network.

The platform 1216 may abstract resources and functions to connect thecomputing device 1202 with other computing devices. The platform 1216may also serve to abstract scaling of resources to provide acorresponding level of scale to encountered demand for the resources1218 that are implemented via the platform 1216. Accordingly, in aninterconnected device embodiment, implementation of functionalitydescribed herein may be distributed throughout the system 1200. Forexample, the functionality may be implemented in part on the computingdevice 1202 as well as via the platform 1216 that abstracts thefunctionality of the cloud 1214.

CONCLUSION

Although the invention has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the invention defined in the appended claims is not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as example forms of implementing theclaimed invention.

What is claimed is:
 1. In a digital medium environment to transform adigital document based on an edit suggestion, a method implemented by atleast one computing device, the method comprising: processing, by the atleast one computing device, code of a digital document to identify dataembedded in the code that identifies a network-based platform thatpublishes the digital document, wherein the network-based platform isidentified and differentiated from multiple different network-basedplatforms that publish digital documents; determining a page type thatis specific to the identified network-based platform for a digital pageof the digital document; extracting, by the at least one computingdevice, a set of editable page elements from the digital page bymatching page elements from the digital page to categories of editablepage elements, wherein the categories of editable page elements areidentified based on the page type of the identified network-basedplatform; generating, by the at least one computing device, visualrepresentations of the editable page elements that each include an editsuggestion for editing a respective page element of the editable pageelements; and transforming, by the at least one computing device, thedigital document by modifying a particular editable page element basedon an edit interaction with one or more of the particular editable pageelement or a respective visual representation of the editable pageelement.
 2. A method as described in claim 1, wherein the data embeddedin the code comprises one or more of a metatag or a library functionthat identifies the page type.
 3. A method as described in claim 1,wherein said extracting the set of editable page elements comprisesparsing, by the at least one computing device, a document object model(DOM) of the digital page to identify the editable page elements fromthe DOM.
 4. A method as described in claim 1, wherein a particular editsuggestion includes a plain text description of an edit recommendationfor editing a respective editable page element.
 5. A method as describedin claim 1, further comprising determining, by the at least onecomputing device, an edit recommendation for the respective page elementbased on historical performance data for other instances of digitalpages that include page elements in a category of editable page elementsrepresented by the respective page element.
 6. A method as described inclaim 5, wherein the historical performance data indicates how aparticular edit to the page elements of the other instances of digitalpages affected user interaction with the other instances of digitalpages.
 7. A method as described in claim 1, further comprising:rendering, by the at least one computing device, a graphical userinterface (GUI) that includes the digital document with the editablepage elements, and the visual representations of the editable pageelements separately from the digital document; and receiving, by the atleast one computing device, the edit interaction as input to therespective visual representation of the editable page element.
 8. Amethod as described in claim 1, further comprising: rendering, by the atleast one computing device, a graphical user interface (GUI) thatincludes change log entries for previous edits to the editable pageelements; and displaying, by the at least one computing device, aneffect affect of a particular edit to a particular editable page elementon performance of the digital page.
 9. A system implemented in a digitalmedium environment to provide edit suggestions for transforming adigital document, the system comprising: at least one processor; andmemory having stored thereon computer-readable instructions that areexecutable by the at least one processor to perform operationscomprising: processing code of the digital document to identify dataembedded in the code that identifies a network-based platform thatpublishes the digital document, wherein the network-based platform isidentified and differentiated from multiple different network-basedplatforms that publish digital documents; determining a page type thatis specific to the identified network-based platform for a digital pageof the digital document; extracting an editable page element from adigital page by matching the editable page element to a category ofeditable page elements identified based on the page type of the digitalpage of the digital document, wherein said extracting the editable pageelement from the digital page comprises matching the editable pageelement from the digital page to a category of editable page elementsidentified based on the page type of the identified network-basedplatform; determining an edit suggestion for editing the editable pageelement, and an edit recommendation for how to edit the editable pageelement based on historic performance data for other instances ofdigital pages that include page elements in the category of editablepage elements, the historic performance data indicating that an increasein user interactions with one or more of the other instances of digitalpages occurred after the edit recommendation was applied to one or morepage elements in the category of editable page elements in the one ormore of the other instances of digital pages; generating, by the atleast one computing device, a visual representation of the editable pageelement that includes the edit suggestion and the edit recommendation;and transforming the digital document by modifying the editable pageelement based on an edit interaction with the visual representation ofthe editable page element.
 10. A system as described in claim 9, whereinsaid matching the editable page element to a category of editable pageelements comprises: processing the code of the digital document toidentify data embedded in the code that identifies the page type andthat includes page elements of the digital page; and comparing the pageelements to multiple different categories of editable page elements tomatch the editable page element to the category of editable pageelements.
 11. A system as described in claim 9, wherein the historicperformance data comprises an indication of an effect of a particularedit on performance of the one or more of the other instances of digitalpages, and wherein the operations further comprise rendering a graphicaluser interface (GUI) that identifies the particular edit and the effectof the particular edit on performance of the one or more of the otherinstances of digital pages.
 12. A system as described in claim 9,wherein said transforming generates an edited digital document, andwherein the operations further comprise: ascertaining performanceattributes of the edited digital document based on user interactionswith the edited digital document; and generating performance data thatassociates the edit interaction with the performance attributes for theedited digital document.
 13. A system as described in claim 9, whereinthe user interactions comprise one or more of user visits to the one ormore of the other instances of digital pages, user purchases via the oneor more of the other instances of digital pages, or user registrationsvia the one or more of the other instances of digital pages.
 14. Asystem as described in claim 9, wherein said extracting the set ofeditable page elements comprises parsing, by the at least one computingdevice, a document object model (DOM) of the digital page to identifythe editable page elements from the DOM.
 15. In a digital mediumenvironment to transform a digital document based on an edit suggestion,a method implemented by at least one computing device, the methodcomprising: processing, by the at least one computing device, a digitaldocument to identify a content platform that publishes the digitaldocument, wherein the content platform is identified and differentiatedfrom multiple different network-based platforms that publish digitaldocuments; extracting, by the at least one computing device, a set ofeditable page elements from a digital page of the digital document;presenting, by the at least one computing device, an edit prompt thatidentifies the identified content platform that publishes the digitaldocument, identifies a page type for the digital page of the digitaldocument, and includes selectable control that is selectable to initiatean edit mode for the digital page; rendering, by the at least onecomputing device and in response to selection of the selectable control,a graphical user interface (GUI) that includes the digital page with theeditable page elements, and visual representations of the editable pageelements displayed separately from the digital page, the visualrepresentations each including an edit suggestion for editing arespective page element of the editable page elements; receiving, by theat least one computing device, input to a particular visualrepresentation of an editable page element, the input indicating an editto be applied to the editable page element; and transforming, by the atleast one computing device, the digital page by modifying the editablepage element based on the input.
 16. A method as described in claim 15,further comprising: rendering, by the at least one computing device, anedit menu in response to the input to the visual representation of theeditable page element; and receiving, by the at least one computingdevice, content input to the edit menu, wherein said transformingcomprises modifying the editable page element with the content.
 17. Amethod as described in claim 16, wherein said rendering the edit menucomprises including in the edit menu a recommendation for editing theeditable page element.
 18. A method as described in claim 15, whereinsaid receiving input to the particular visual representation and saidmodifying the editable page element are performed independent of userinteraction with the digital document.
 19. A method as described inclaim 15, wherein the GUI further includes a recommendation for editinga particular editable page element in a category of editable pageelements, wherein the recommendation is based on historic performancedata for other instances of digital pages that include page elements inthe category of editable page elements, the historic performance dataindicating that an increase in user interactions with one or more of theother instances of digital pages occurred after the edit recommendationwas applied to one or more page elements in the category of editablepage elements in the one or more of the other instances of digitalpages.
 20. A method as described in claim 19, wherein the userinteractions comprise one or more of user visits to the one or more ofthe other instances of digital pages, user purchases via the one or moreof the other instances of digital pages, or user registrations via theone or more of the other instances of digital pages.